What shipped, and when.

Point an address at Herald and every reply arrives at a webhook as a structured document: the typed reply separated from the quoted text, attachments as signed URLs, and SPF, DKIM, and DMARC results on the payload. Replies to messages Herald sent carry the original id so threads stitch themselves together.

Inbound is on every plan. Setup is one MX record.

An API key now lists the tools it may call. Create one with draft and stats for an agent you are still getting to know, then add send later. A denied call returns a clear error the skill file teaches the agent to surface rather than retry.

The window in which a repeated Idempotency-Key returns the original message instead of sending again has grown from 24 hours to seven days. Retries from queued jobs that ran late no longer produce duplicates.

• The header is now required on sends from agent-scoped keys.
• The response includes idempotent_replay: true when a key matched.

For about six hours on 21 July, messages deferred by one large mailbox provider showed as delivered in the log and in the stats. Delivery itself was unaffected — every message eventually went out — but the log lied about the timing. The entries have been corrected and the status mapping now treats an unknown response code as deferred, never delivered.

A new domain now ramps automatically: engaged contacts first, a daily cap that roughly doubles while bounce and complaint rates stay low, overflow to Herald's warm shared pool, and a pause with an explanation if complaints spike. The schedule is visible on the domain page. Most senders reach a hundred thousand a day in about three weeks.

Every account can now hold several workspaces, each with its own domains, contacts, templates, and keys. Usage rolls up to one invoice at the end of the month, itemised per workspace, so agencies and platforms can see which client sent what. Switch between them from the menu in the top left.